Repository navigation
spec(FIX-1788): amendment 1 · worker named at session create; fold round two - #2818
Conversation
…und two #2812 merged before its round-two review was folded. This amendment: - Q1 decided as copy (now D3); D1 and D2 recorded as signed. - D4: a session's worker is named once, at create, in a server-only field on the session record (epic D3 change 3, as #2813 records). The engine runs a flow-declared create check on every path that writes a new session record; actions never carry `worker`; no session without one. - The same S1 mechanism holds server-written session state that changes after create (FIX-1791's delegates). - App API: today's client plus `worker` on createSession/listSessions, the roster's `flow`, and Workforce's findWorkerSession / ensureWorkerSession (one criteria object; racing ensure calls make one session via a derived id and the create's insert-if-absent write). - Worker edited to another flow, forked, fired: rules for its sessions. - Purges the lab-only `clients.actions(...)` example; retires seat, person and kind in prose; aligns with FIX-1789's `workerFlows` and `writtenBy.workerId`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Second look + architecture pass (spec-only PR, read against
|
Architect: coherence with FIX-1791 (#2815), one key to nameThis matches epic D3 Locks in (3) on
Nothing else crosses: #2814's |
Coherence note: finding #2 crosses into #2815 (FIX-1791)Before you fold finding #2 (cut or justify S1's server-written session-state fields), note that the open FIX-1791 spec #2815 already depends on this PR for that mechanism. Its How line says: "one coordinator flow keeps the delegates in session state that only the server writes ([FIX-1788])". If this PR takes option (a) and cuts it, while #2815 stays as written, each spec points at the other for the mechanism and nobody builds it. Pick one owner and make both specs say the same thing:
Either is fine. What we must avoid is the two specs disagreeing about who builds it. Also, check that epic D3 change 3 (as amended in #2813) doesn't already settle this before you choose. Findings #1, #3, #4 and #5 don't touch another in-flight stream, so no coherence concern there. |
There was a problem hiding this comment.
Simplify / approach review (FIX-1788 amend 1)
This is a spec-only PR (~1.7k lines): retained FIX-1788 issue spec + FIX-1786 epic sync + one retained POC (poc/flow-inventory/). I did not find production-code complexity to trim here; the interesting question is whether the documented implementation plan is heavier than the problem requires.
Verdict on the approach
The core architectural bet looks right and is hard to simplify without trading away safety or migration:
- Worker named at session create (D4) is cleaner than first-turn linking or per-message worker fields — fewer app call sites, aligns with “session owns the worker,” and matches Jake’s #2812 direction.
- One flow copy per kind (D3 / S10) vs per-hire registration is the real simplification win at runtime; the spec correctly pays migration cost in P3/P4 rather than stranding hires mid-stack.
- Thin Workforce on generic S1 create-check +
worker/workerIdon the client keeps the engine workforce-agnostic; that layering is appropriate even though it adds surfaces (S1 + S5 + S5a).
I do not think a materially simpler product design exists without reopening epic gates (org-scoped workers, caller-seeded links, or keeping per-hire flow copies).
Where complexity did grow (and what I’d do instead)
| Area | Smell | Lighter path (spec hygiene, not re-architecture) |
|---|---|---|
| Procedural contract in two places | DECISIONS.md §“Decided, not asked” largely restates PLAN.md Surfaces / Guardrails / Sketch |
Keep D1–D4 outcomes + fork/library seam in DECISIONS; link to Plan for S1–S16 and checks. You already recorded this in Plan §“Notes from review” — worth doing before implementers treat both as canonical. |
| S5 vs S6–S8 | Three PLAN rows + per-turn load/grants/state for one “execution slice” | Consider one deep module (resolveWorker / single interface) as noted in Plan notes from #2812; optionally one PLAN surface row with sub-bullets for config · keyed resources · grants (table-only cleanup). |
| Naming layers | DOCS.md drafts createCheck/link/createWorkerHireBlocks while Plan pins worker / workerId |
Add the “shipped names” box Plan §Pinned names asks for at the top of DOCS.md (or align draft tables now). Reduces P4 doc churn. |
| V0 evidence | WORKER.md totality is automated; hireWorkforce census is manual rg |
Optional sibling POC under poc/ (FIX-1503 / FIX-1748 census style) — not required for direction approval, but avoids asymmetric evidence. |
| Retained POC | inventory.mjs re-implements frontmatter/flow rules |
Fine for throwaway evidence; implementation must reuse readDeclaredFlow, loader walks, and discoverWorkforceCode — don’t copy POC heuristics into product code. |
Performance (at implement time, not this PR)
When built: watch listSessions({ worker }) without a store index (S5a) and per-turn worker load + name resolution (S6–S8). Spec is correct to require per-turn freshness; implementation should cache within a run where the rules allow.
Must-fix before merge
D4’s one-line tagline under the figure contradicts the chosen horn (still describes first-turn / message-shaped linking). The figure alt text and “Considered and dropped” table say the opposite — easy for a skim-reader to implement the wrong thing.
Minor nits (optional)
- S10 still says “in whichever declaration shape the epic recorded” — epic Q1 is now list; tighten wording.
- Stale parallel between BR “Proved by” and PLAN V-ids — pick one owner (also in Plan notes).
Summary: Directionally approve the design; request one spec correction (D4 tagline) and encourage folding the review-round simplifications you already captured in Plan §“Notes from review” so the retained set has a single procedural owner before implementation PRs land.
Sent by Cursor Automation: Review For Best Approach
|
|
||
|  | ||
|
|
||
| It comes down to what carries the worker: on the first turn, every message shape carries it. |
There was a problem hiding this comment.
Must fix: This line still states the rejected D4 horn (“on the first turn, every message shape carries it”). The card above, the figure alt text (L101), and the “Considered and dropped” row for first-turn linking all describe create-time linking.
Suggest replacing with something aligned with the chosen outcome, e.g. “It comes down to what carries the worker: the session, once, at create — so messages never name one.”
There was a problem hiding this comment.
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status
Fixed in 5226872. The tagline now states the chosen option: "It comes down to what carries the worker: the session, once, at create, so messages never name one."
Generated by Claude Code
| | S8 | `workforce` · grants per turn | A worker's document grants and reference wall narrow what its model reaches on each turn: tools and context. Replaces the per-copy narrowed resource map | BR-24 | | ||
| | S9 | `workforce` · hire, fork, fire | Writes to S3, through the existing hire blocks and tool; fork is new beside them. Each turn names the collection it wrote | BR-1 BR-2 BR-4 BR-7 BR-8 | | ||
| | S9 | `workforce` · hire, fork, fire | Writes to S3, through the hire blocks and tool; fork is new beside them and copies per D3. The hire blocks take `workerFlows` (FIX-1789) and, since they change here, take a worker name (the docs draft `createWorkerHireBlocks`; not pinned). Each turn names the collection it wrote | BR-1 BR-2 BR-4 BR-7 BR-8 BR-19c | | ||
| | S10 | `workforce` · registration | The hire registers one copy per flow, `agent` and every flow handed to it, with no per-worker copy and no pin. The `agent` flow becomes a singleton, in whichever declaration shape the epic recorded | BR-26 | |
There was a problem hiding this comment.
After epic Q1 closure (list at FIX-1789 gate), this reads stale. Consider: “…registers on the installation’s workerFlows list (epic Q1).” — drops “whichever declaration shape” ambiguity.
There was a problem hiding this comment.
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status
Fixed in 5226872. S10 now reads: "The agent flow becomes a singleton and registers on the installation's workerFlows list (epic Q1)."
Generated by Claude Code
| renamed here (S9). | ||
|
|
||
| ## Notes from review | ||
|
|
There was a problem hiding this comment.
+1 on acting on this note before implementation: S5 + S6 as one deep module (resolveWorker → { worker, resolved config } + link path) would cut cross-coupling without changing the four-PR stack. Worth a single explicit line under S5/S6 in the Surfaces table if you adopt it.
There was a problem hiding this comment.
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status
Adopted in 5226872. S5 now says S5 and S6 are built as one module with one interface (resolveWorker returns the worker plus its resolved configuration, beside the create check), on the same PR stack.
Generated by Claude Code
| pin (the session-state option, the upgrade command, `fork`) are reconciled with the shipped | ||
| code before publishing. Q1's answer sets one sentence, marked below. | ||
| ([`user-docs.md`](../../../docs/contributing/user-docs.md)) and uses the new terms: worker, | ||
| worker flow, user. Pinned names are `PLAN.md`'s. Draft names, reconciled with the shipped code |
There was a problem hiding this comment.
Simplification for P4: Plan already pins public names (worker, workerId, helpers). This paragraph mixes draft API names (createCheck, link, createWorkerHireBlocks) with pinned ones. A short shipped names box (or aligning the session-table draft to worker on create) would avoid implementers/docs re-litigating exports — matches Plan §“Notes from review”.
There was a problem hiding this comment.
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status
Added in 5226872: a Shipped names box at the top of DOCS.md. Pinned: worker on createSession, worker on listSessions, the roster's flow, findWorkerSession, ensureWorkerSession (plus FIX-1789's workerFlows). Drafts: createCheck and its link input, serverOwned, createWorkerHireBlocks, fork, useFlow's worker, fsdev run --worker, the upgrade command.
Generated by Claude Code
…791 key - Architect (6024892197): reserve FIX-1791's coordinator-conversation criteria key beside FIX-1794's and FIX-1793's (S5a, pinned names, EVOLUTION); BR-18a/S5a: a delivery opens the delegate's session via ensureWorkerSession with the worker named. - Second look (6024879316): S1 is one session-birth function owning purge, create check and insert-if-absent; handleCreateSession and ensureSessionRecord become thin callers; fsdev run is the fourth path (--worker, V1 case); check on the miss path only (V1 case); 409 belongs to the create route, the action path adopts; one exported id derivation on the tenant-resolved key; ensure returns the most recent match; delete-then-ensure V4 case; workerId is the value in a generic engine key; "Decided, not asked" trimmed to what PLAN doesn't hold. - Coherence (6024896388): server-written state stays here (epic D3 Locks in (3)), FIX-1791's delegates (#2815) consume it. - Cursor (5434236373): D4 tagline states the chosen option; S10 names the workerFlows list; DOCS shipped-names box; S5 and S6 as one module. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f186b8b588
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | ID | Package · role | Change | Rules | | ||
| |---|---|---|---| | ||
| | S1 | `engine` + `core` · session state declaration, the session create route | A flow can declare session-state fields server-owned. The create route refuses caller state for them with 400, naming the field; only flow code writes them. Unset means today. FIX-1791 keeps delegates here too | BR-15 BR-16 | | ||
| | S1 | `engine` + `core` + `client` + `react` · server-owned session data, at create | One declaration, two parts. **A create field:** the flow declares a create check; every path that writes a new session record for it (the create route, the record an action writes for a missing session id, a transport's session resolver) calls it with the verified principal and the create's input before the insert-if-absent write. It refuses, or returns a value the engine stores on the record outside `state`; no route writes it afterwards. A path with no input is refused. **Server-written state:** session-state fields the create refuses from a caller (400, naming the field) and only flow code writes; FIX-1791's delegates live here. The list route filters on the create field. The client's `createSession` takes `worker` and `listSessions` a `worker` filter, mapped onto that field; `useFlow` passes `worker` to both. The engine knows no worker. Undeclared means today | BR-13 BR-14 BR-15 BR-16 BR-18a | |
There was a problem hiding this comment.
Route dispatched child creation through the create check
When a task dispatcher targets a worker flow, create-request-host.ts writes the derived child SessionRecord directly before the target task entry executes. This path is absent from S1's supposedly exhaustive list, so S5 cannot enforce the check from the task entry after the unlinked record already exists; dispatched worker sessions will either lack workerId or fail on their first turn. Carry the worker/create input through this direct writer, run the create check there, and cover it in V1/V4.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status
Fixed in 99430a6.
- PLAN S1 lists the dispatched-child writer (
engine/src/context/create-request-host.ts) as the fifth path and routes it through the one session-birth function. The worker is carried from the dispatching flow's code, so the child is born linked. - The guardrail now reads: every
SessionRecordinsert goes through the birth function. It is enforced by construction, and V1 includes a grep that finds no othersession.set(…, "absent")writer. - V1 and V4 add a task dispatched to a worker flow.
Generated by Claude Code
| | S5 | `workforce` · the link, one module | The check (the session user's own worker or a standard one · names this flow · no link yet) and the server-owned write, atomic per session: two racing first turns link one worker. The door's per-session concurrency or a versioned write, your pick; no Layer 1 change. The door, the task entry and the mailbox wake all call it | BR-10–14 BR-13a BR-18 BR-19 BR-19a | | ||
| | S6 | `workforce` · per-turn configuration | Load the linked worker each turn; resolve tool, skill, package, capability and worker-folder names against what the installation registers; refuse a turn whose names don't resolve, or whose flow is now standard-only. Every read of a worker setting moves off `ctx.flow.config` to it | BR-20–22a | | ||
| | S5 | `workforce` · the link, one module | The create check every worker flow declares through S1: a worker is named; it is the principal's own (read at their scope) or a standard one; it names this flow; a derived worker-session id is the caller's. It returns `workerId`. The task entry and the mailbox wake open sessions through it, naming the worker from the dispatching flow's code. No turn sets or changes a link | BR-10–14 BR-13b BR-18 | | ||
| | S5a | `workforce` · `findWorkerSession`, `ensureWorkerSession` | One lookup path over `listSessions({ …, worker })`, taking one criteria object. FIX-1788 ships `worker`; leave the object open for FIX-1794's and FIX-1793's keys, and define neither. `find` returns the caller's most recent matching session, or none. `ensure` finds, or creates on the flow the worker's roster row names, at an id derived from the caller's user, org and criteria; a 409 from the create means a racing call won, so it reads that id and returns it (the store's own create guarantee: SQLite, Postgres, one filesystem store instance). Where the helpers get the caller and transport is yours | BR-13a BR-14a | |
There was a problem hiding this comment.
Change ensured-session identity when a worker changes flow
When BR-19b edits a worker to use another flow, this worker-only lookup can return the now-unusable old-flow session. Even if lookup is narrowed to the current flow, the specified derived ID still uses only (user, org, criteria), and FIX-1788's sole criterion is the unchanged worker ID; creating the replacement therefore collides with the old session, takes the 409 path, and returns that same refusing session. Include the resolved flow or worker incarnation in reuse and ID derivation, and verify BR-19b through ensureWorkerSession.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status
Fixed in 99430a6.
- S5a: both helpers resolve the worker's current flow from the roster first. The lookup and the derived id include that resolved flow, not just the criteria.
- After BR-19b's edit,
ensureWorkerSessionfinds nothing on the new flow and creates a fresh session at a new id. The old sessions keep refusing. - BR-19b says so, and V4 drives BR-19b through
ensureWorkerSession.
Generated by Claude Code
| | S5 | `workforce` · the link, one module | The check (the session user's own worker or a standard one · names this flow · no link yet) and the server-owned write, atomic per session: two racing first turns link one worker. The door's per-session concurrency or a versioned write, your pick; no Layer 1 change. The door, the task entry and the mailbox wake all call it | BR-10–14 BR-13a BR-18 BR-19 BR-19a | | ||
| | S6 | `workforce` · per-turn configuration | Load the linked worker each turn; resolve tool, skill, package, capability and worker-folder names against what the installation registers; refuse a turn whose names don't resolve, or whose flow is now standard-only. Every read of a worker setting moves off `ctx.flow.config` to it | BR-20–22a | | ||
| | S5 | `workforce` · the link, one module | The create check every worker flow declares through S1: a worker is named; it is the principal's own (read at their scope) or a standard one; it names this flow; a derived worker-session id is the caller's. It returns `workerId`. The task entry and the mailbox wake open sessions through it, naming the worker from the dispatching flow's code. No turn sets or changes a link | BR-10–14 BR-13b BR-18 | | ||
| | S5a | `workforce` · `findWorkerSession`, `ensureWorkerSession` | One lookup path over `listSessions({ …, worker })`, taking one criteria object. FIX-1788 ships `worker`; leave the object open for FIX-1794's and FIX-1793's keys, and define neither. `find` returns the caller's most recent matching session, or none. `ensure` finds, or creates on the flow the worker's roster row names, at an id derived from the caller's user, org and criteria; a 409 from the create means a racing call won, so it reads that id and returns it (the store's own create guarantee: SQLite, Postgres, one filesystem store instance). Where the helpers get the caller and transport is yours | BR-13a BR-14a | |
There was a problem hiding this comment.
Specify identity and transport for the session helpers
In browser or Node clients using a non-default base URL or the framework's default identity resolver, findWorkerSession({ worker }) and ensureWorkerSession({ worker }) have no client transport, userId, or roster context from which to discover the flow and create/list sessions. The existing session client requires a constructed transport and non-empty flowKind/userId, so leaving where these values come from to the implementer makes the pinned context-free API impossible without inventing ambient state or a new endpoint. Pin a bound-client/factory or explicit options contract and update the examples accordingly.
AGENTS.md reference: AGENTS.md:L78-L78
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status
Fixed in 99430a6.
- The helpers are methods on a bound client:
createWorkforceClient({ userId, baseUrl?, apiPath?, fetcher? }). Those are the same transport options ascreateSessionClient. - React gets them from a hook over the same client. The hook name is a draft.
- There is no ambient state and no new endpoint: the methods use the roster read and the session client.
createWorkforceClientand its two method names are pinned (PLAN Pinned names). The SPEC, DOCS and PR-body examples useworkforce.ensureWorkerSession({ worker: "researcher" }).
Generated by Claude Code
|
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status Folded in 5226872.
(re: comment 6024892197) Generated by Claude Code |
|
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status Folded in 5226872.
(re: comment 6024879316) Generated by Claude Code |
|
from: fsd-head-of-engineering / session: em-fix-1786 / kind: status Folded in 5226872 as option (b), kept here. Epic D3 Locks in (3) on (re: comment 6024896388) Generated by Claude Code |
Architect: round-two fold checked, coherent with #2815Checked 5226872 against both of my asks. Both match.
No fork remains. The merge order stands: this PR merges first, then #2815. |
…sure, bound client
- 4200172850 (P1): the dispatched-child writer (create-request-host.ts)
is the fifth SessionRecord insert path; it routes through the one
birth function and carries the worker. Guardrail: every SessionRecord
insert goes through the birth function; V1 greps for other "absent"
writers. V1/V4 cover a task dispatched to a worker flow.
- 4200172858 (P1): the helpers' lookup and derived id include the
worker's resolved flow, so after BR-19b's edit ensureWorkerSession
creates a fresh session on the new flow; V4 drives BR-19b through it.
- 4200172866 (P2): the helpers are methods on a bound
createWorkforceClient({ userId, baseUrl?, apiPath?, fetcher? }); React
gets them from a hook over the same client. Pinned; SPEC and DOCS
examples updated. No ambient state, no new endpoint.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV


The problem
The FIX-1788 spec merged in #2812 before its round-two review was folded. The merged text still says a session learns its worker from the first message, so every message an app sends would carry
worker. You said the worker belongs to the session, and that a session's worker can't change. Its app example also usedclients.actions(...), which is a private Shift Manager lab wrapper, not a framework API.What this does
It records your gate answers and moves the worker to session create. It changes only
specs/issues/FIX-1788/. Nothing is implemented.worker.flow.createSessionClient().createSessiontakes aworkeroption andlistSessionstakes aworkerfilter. A boundcreateWorkforceClient({ userId, baseUrl })(the session client's transport options) has two methods:ensureWorkerSession({ worker })finds the user's session or creates one, andfindWorkerSessiononly checks. After that,createClient({ flowKind }).sendAction(action, input, { sessionId })works as it does today. The helpers take one criteria object, so FIX-1794 and FIX-1793 can add keys to it later.ensureWorkerSessioncreates the session at an id derived from the user, the org and the criteria. When two calls race, the store's existing insert-if-absent write gives the second call a 409, and that call returns the first session. The create check refuses a derived id that belongs to someone else.clients.actions(...)example is removed. The examples use only the public@flow-state-dev/clientexports (createSessionClient,createClient) and the two helpers. Prose no longer says "seat", "person" or "kind". The draft docs teachcreateWorkerHireBlocks({ workerFlows }), which matches FIX-1789's rename ofkinds(#2814).writtenBy.workerIdcomes from the link.import { createClient } from "@flow-state-dev/client" + import { createWorkforceClient } from "@flow-state-dev/workforce" - const researcher = createClient({ flowKind: "acme.~alice.researcher", userId }) - await researcher.sendAction("run", { message }, { sessionId }) + const workforce = createWorkforceClient({ userId, baseUrl }) + const session = await workforce.ensureWorkerSession({ worker: "researcher" }) + const agent = createClient({ flowKind: session.flowKind, userId }) + await agent.sendAction("run", { message }, { sessionId: session.id })What's asked of you
Approve this amendment: is the worker named at session create, as you meant?
ensureWorkerSession({ worker: "researcher" })and then sends ordinary messages. A session can't exist without a worker, and its worker can't change. Talking to a different worker means a different session.Implementation of FIX-1788 waits for this amendment to merge.
Parts worth reviewing closely
DECISIONS.md→ D4, andPLAN.md→ S1: one session-birth function that every path reaches,fsdev runincluded. It owns the purge, the create check and the insert-if-absent write, and it holds the delegates' server-written state.BUSINESS-RULES.md→ BR-10 to BR-19c. The session rules, rewritten for create time. BR-13a covers racing calls, BR-13b squatting, BR-18a delegates, BR-19b and BR-19c an edit and a fork.PLAN.md→ S1, S5, S5a and Pinned names. S1 now includesclientandreact, becauseuseFlowpassesworkerthrough. Pinned app-facing names are onlyworkeron create,workeron list, the roster'sflow,findWorkerSessionandensureWorkerSession.SPEC.md→ the goal check. Leg b's signal is reworked. Thecaller-linkcontrol still fails: under it, the server accepts the create's caller state and reads the link from it.Links: original review #2812 (decision threads on SPEC.md L67: 1, 2, 3, 4; fold checklist 6024339940; gate answers 6024643873) · epic amendment #2813 · FIX-1789 amendment #2814 · retained spec
specs/issues/FIX-1788/· FIX-1788 · epic FIX-1786 · this PR merges intomainafter your approvalHow to review this
This is a direction amendment, not an implementation. The question is whether the approach is right. This round changed the approach in one place, where a session learns its worker, and the rest follows from that: the app API, the rules and the plan.
Contract and verification
specs/issues/FIX-1788/. Never pushed tospec/FIX-1788or spec(FIX-1788): A worker is a private resource its owner holds, run by the shared flow it names #2812.spec-figures.md→ Verify): fences balanced; no risky mermaid labels; every SVG has ext=0, one theme block, one aria-label and ≤96 lines; every nav line is present; every decision card (D1 to D4) has its trade-off figure; no figure is missing;node scripts/validate-spec-folder.mjspasses.d4-link-at-create.svg(new),d3-fork-copies.svg(wasopen-fork.svg, now CHOSEN),d2-org-wide-hire.svg,what-changes.svg.node specs/issues/FIX-1788/poc/flow-inventory/inventory.mjs→ PASS, 23 flows over 94 of 94WORKER.mdfiles.CONTROL=drop-one→ exit 1. Only its README wording changed.packages/client/src/index.ts:createClient,createTypedClientandcreateSessionClientare exported,SessionDetailcarriesflowKind, andsendAction(action, input, { sessionId })matches.99430a6) folds Codex: a fifth birth path (the dispatched-child writer), a lookup and derived id that are aware of the worker's flow, and the boundcreateWorkforceClient.5226872) folds the review on this PR: the architect (6024892197), the second look (6024879316), the coherence note (6024896388) and Cursor (5434236373).🤖 Generated with Claude Code
https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
Generated by Claude Code